I’ve heard it said that as “source” I should handle something way outside my general activity.

An org board is a list of hats with seniorities. The hats are in flow sequence.

This is a confusion between SOURCE and CAUSE.

A hat is a duty. It outlines the actions necessary to accomplish a production and receive what’s needed, change and route it.

You are CAUSE over your area. Results are the effect of your own efforts. When these support general programs we all win.

In theory the I/C holds all functions. When he doesn’t fully outline them they can’t be hatted. If they’re not hatted he wears them as an unknown fog. Simple as that.

You should not minimize yourself as CAUSE. It Is your greatest ability.

What defines a hat is a product.

Being blamed sometimes blunts Being Cause. But if one’s total ambition is to be blameless the best situation is to get one’s name on a tombstone. And it’s no fun being dead.

If you count up the expected products you get the minimum number of hats. The steps to get the product is the hat. Products are also composed of lesser products, so hats can be enlarged. It’s what you designate as a product that makes a hat. It’s the importance of that product to others on the line that makes the hat’s importance.

Being CAUSE over matter, energy, space, time, force, form, location and life is just another way of saying “OT”.

The completeness and size of the product make the seniority of the hat.

The overall product of a division determines the hat of the divisional officer. The lesser products that when combined make the overall product determine the rest of the division hats.

Until you can define in one go the overall product of a division you aren’t likely to be able to post any real part of its org board. For the product of hats of that div add up to the div product.

When you see an unposted or unreal org board, the head of the div is not producing a product with that div, no matter how busy it all looks or how exhausting.